Managing tune-aways in a multi-subscription multi-standby communication device

ABSTRACT

Various embodiments include a device processor that may monitor a data loss from a broadcast data stream received by a radio frequency (RF) resource of a multi-subscription multi-standby (MSMS) communication device using a first subscription. In response to determining that an amount of the monitored data loss plus an amount of expected data loss from anticipated tune-aways to a second subscription and a third subscription does not meet a first data loss threshold, the device processor may determine whether an amount of the monitored data loss plus an amount of expected data loss from an anticipated tune-away to a third subscription meets a second data loss threshold. The device processor may prevent the tune-away to the third subscription in response to determining that the amount of the monitored data loss plus the expected data loss from the anticipated tune-away to the third subscription meets the second data loss threshold.

BACKGROUND

A multi-subscription multi-standby communication device may include oneor more Subscriber Identity Module (SIM) cards that provide users withaccess to multiple separate mobile telephony networks. Each SIM may beassociated with a different service provider subscription, enabling themulti-subscription multi-standby communication device to communicatewith one or more communication networks. Each SIM or subscription mayalso be associated with a radio access technology (RAT).

A multi-subscription communication device that includes one or more SIMsand connects to two or more separate mobile telephony networks using oneor more shared radio frequency (RF) resources/radios may be termed a“multi-standby” communication device. One example of amulti-subscription multi-standby communication device is adual-SIM-dual-standby (DSDS) communication device, which includes twoSIM cards that share a set of radio frequency (RF) circuitry (referredto as an “RF chain” or a “RF resource chain”) to communicate with twoseparate mobile telephony networks on behalf of their respectivesubscriptions. Another example is a single-radio LTE (SRLTE)communication device, which includes one SIM card/subscriptionassociated with two (or more) subscriptions that share a single sharedRF resource chain to communicate with one or more multi-subscriptionmulti-standby communication networks on behalf of the multiplesubscriptions.

At certain times the multiple subscriptions sharing an RF resource chainmay need to use the RF resource to communicate with their respectivemobile networks simultaneously. Therefore, the communication device mayperiodically force one subscription to interrupt its RF operations sothat another subscription may use the shared RF resource chain toperform communication operations, a process called a “tune-away,” sincethe RF resource chain must tune away from the frequency bands and/orchannels of the first subscription and must tune to frequencybands/channels of the second subscription. As a result of the tune-away,data received using the active subscription may be lost or corrupted andthus difficult or impossible to decode. The problem of data loss duringa tune-away is exacerbated when the first subscription is conductingcommunications that are particularly sensitive to latency or data loss,such as streaming media, for example, eMBMS (Evolved MultimediaBroadcast Multicast Service).

SUMMARY

The various embodiments include methods and multi-subscriptionmulti-standby communication devices implementing methods for managing atune-away by an RF resource of the multi-subscription multi-standbycommunication device. The various methods may include monitoring anamount of data loss from a broadcast data stream received by the MSMScommunication device using a first subscription, determining an amountof expected data loss from anticipated tune-aways from the firstsubscription to a second subscription, determining an amount of expecteddata loss from anticipated tune-aways from the first subscription to athird subscription, determining whether the amount of the monitored dataloss plus the amount of expected data loss from anticipated tune-awaysfrom the first subscription to the second subscription plus the amountof expected data loss from anticipated tune-aways from the firstsubscription to the third subscription meets a first data lossthreshold, determining whether an amount of the monitored data loss plusan amount of expected data loss from a next anticipated tune-away fromthe first subscription to the third subscription meets a second dataloss threshold in response to determining that the amount of themonitored data loss plus the amount of expected data loss fromanticipated tune-aways from the first subscription to the secondsubscription plus the amount of expected data loss from anticipatedtune-aways from the first subscription to the third subscription doesnot meet the first data loss threshold, and preventing a tune-away ofthe RF resource from the first subscription to the third subscription inresponse to determining that the amount of the monitored data loss plusthe amount of expected data loss from the next anticipated tune-awayfrom the first subscription to the third subscription meets the seconddata loss threshold.

Some embodiments may further include permitting the tune-away of the RFresource from the first subscription to the third subscription inresponse to determining that the amount of the monitored data loss plusthe amount of expected data loss from the next anticipated tune-awayfrom the first subscription to the third subscription does not meet thesecond data loss threshold. Some embodiments may further includepermitting a tune-away of the RF resource from the first subscription tothe second subscription after determining whether the amount of themonitored data loss plus the amount of expected data loss from the nextanticipated tune-away from the first subscription to the thirdsubscription meets the second data loss threshold. Some embodiments mayfurther include preventing tune-aways from the first subscription to thesecond subscription and to the third subscription in response todetermining that the amount of the monitored data loss plus the amountof expected data loss from anticipated tune-aways from the firstsubscription to the second subscription plus the amount of expected dataloss from anticipated tune-aways from the first subscription to thethird subscription meets the first data loss threshold.

In some embodiments, preventing a tune-away of the RF resource from thefirst subscription to the third subscription in response to determiningthat the amount of the monitored data loss plus the amount of expecteddata loss from the next anticipated tune-away from the firstsubscription to the third subscription meets the second data lossthreshold may include determining an amount of reduction for a seconddata loss threshold based on an amount of data loss that is attributableto past tune-aways from the first subscription to the secondsubscription, reducing the second data loss threshold by the determinedamount of reduction, determining whether the amount of the monitoreddata loss plus the amount of expected data loss from the nextanticipated tune-away from the first subscription to the thirdsubscription meets the reduced second data loss threshold, andpreventing a tune-away of the RF resource from the first subscription tothe third subscription in response to determining that the amount of themonitored data loss and the expected data loss from the anticipatedtune-away from the first subscription to the third subscription meetsthe reduced second data loss threshold.

Some embodiments may further include permitting the tune-away of the RFresource from the first subscription to the third subscription inresponse to determining that the amount of the monitored data loss plusthe amount of expected data loss from the anticipated tune-away from thefirst subscription to the third subscription does not meet the reducedsecond data loss threshold. Some embodiments may further includedetermining whether a collision between reception of the broadcast datastream and a tune-away from the first subscription to the secondsubscription is detected, and increasing the second data loss thresholdin response to determining that the collision between reception of thebroadcast data stream and the tune-away from the first subscription tothe second subscription is detected. Such embodiments may includeincreasing the second data loss threshold by the determined amount ofreduction in response to determining that the collision betweenreception of the broadcast data stream and the tune-away from the firstsubscription to the second subscription is detected.

Some embodiments may further include continuing to receive segment dataof the broadcast data stream using the first subscription in response todetermining that the collision between reception of the broadcast datastream and the tune-away from the first subscription to the secondsubscription is not detected. Some embodiments may further includedetermining whether another collision between reception of the broadcastdata stream and a tune-away from the first subscription to the secondsubscription is expected, and increasing the second data loss thresholdin response to determining that the another collision between receptionof the broadcast data stream and the tune-away from the firstsubscription to the second subscription is not expected. Suchembodiments may include increasing the second data loss threshold by thedetermined amount of reduction in response to determining that theanother collision between reception of the broadcast data stream and thetune-away from the first subscription to the second subscription is notexpected.

Some embodiments may further include continuing to receive segment dataof the broadcast data stream using the first subscription in response todetermining that the another collision between reception of thebroadcast data stream and the tune-away from the first subscription tothe second subscription is expected. Some embodiments may furtherinclude determining a biased block probability threshold, determining arandom number for a present segment of the broadcast data stream,determining whether the determined random number meets the biased blockprobability threshold, and permitted the tune-aways of the RF resourcefrom the first subscription to the third subscription in response todetermining that the determined random number meets the biased blockprobability threshold. Such embodiments may further include determiningwhether an amount of the monitored data loss plus an amount of expecteddata loss from a next anticipated tune-away from the first subscriptionto the third subscription meets the second data loss threshold inresponse to determining that the determined random number does not meetthe biased block probability threshold.

Various embodiments further include a multi-subscription multi-standbycommunication device having a memory, an RF resource, and a processorcoupled to the memory and the RF resource and configured with processorexecutable instructions to perform operations of the methods describedabove. Various embodiments include a a multi-subscription multi-standbycommunication device having means for performing functions of themethods described above. Various embodiments include a non-transitoryprocessor-readable storage medium having stored thereonprocessor-executable instructions configured to cause a processor of amulti-subscription multi-standby communication device to performoperations of the methods described above.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate exemplary embodiments. Togetherwith the general description given above and the detailed descriptiongiven below, the drawings serve to explain features of variousembodiments, and not to limit various embodiments.

FIG. 1 is a component block diagram of a communication system suitablefor use with various embodiments.

FIG. 2 is a component block diagram of a multi-subscriptionmulti-standby communication device according to various embodiments.

FIG. 3 is a timeline illustrating a reception of segments of a datastream by an RF resource of a multi-subscription multi-standbycommunication device according to various embodiments.

FIG. 4 is a process flow diagram illustrating a method for managing atune-away by an RF resource of a multi-subscription multi-standbycommunication device according to various embodiments.

FIG. 5 is a process flow diagram illustrating another method formanaging a tune-away by an RF resource of a multi-subscriptionmulti-standby communication device according to various embodiments.

FIG. 6 is a process flow diagram illustrating another method formanaging a tune-away by an RF resource of a multi-subscriptionmulti-standby communication device according to various embodiments.

FIG. 7 is a process flow diagram illustrating another method formanaging a tune-away by an RF resource of a multi-subscriptionmulti-standby communication device according to various embodiments.

FIG. 8 is a process flow diagram illustrating another method formanaging a tune-away by an RF resource of a multi-subscriptionmulti-standby communication device according to various embodiments.

FIG. 9 is a component block diagram of a multi-subscriptionmulti-standby communication device suitable for use with variousembodiments.

DETAILED DESCRIPTION

Various embodiments will be described in detail with reference to theaccompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.References made to particular examples and implementations are forillustrative purposes and are not intended to limit the scope of theclaims.

Various embodiments include methods implemented multi-subscriptionmulti-standby communication devices that enable reception of cellbroadcasts on a first network while reducing degradation of throughputof data of an active communication session on a second network byappropriately scheduling tune-aways to the first network.

The terms “multi-subscription multi-standby communication device” and“MSMS communication device” refer to any one or all of cellulartelephones, smartphones, personal or mobile multi-media players,personal data assistants, laptop computers, tablet computers,smartbooks, palmtop computers, wireless electronic mail receivers,multimedia Internet enabled cellular telephones, wireless gamingcontrollers, and similar electronic devices and portable computingplatforms which include a programmable processor, a memory, and one ormore shared RF resources, and which are configured to supportcommunications over two or more subscriptions. Various embodiments maybe particularly useful in any communication devices that can supportmultiple wireless wide area network subscriptions and communicationsessions with two or more communication networks.

The terms “component,” “module,” “system,” and the like as used hereinare intended to include a computer-related entity, such as, but notlimited to, hardware, firmware, a combination of hardware and software,software, or software in execution, which are configured to performparticular operations or functions. For example, a component may be, butis not limited to, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on acommunication device and the communication device may be referred to asa component. One or more components may reside within a process and/orthread of execution and a component may be localized on one processor orcore and/or distributed between two or more processors or cores. Inaddition, these components may execute from various non-transitorycomputer readable media having various instructions and/or datastructures stored thereon. Components may communicate by way of localand/or remote processes, function or procedure calls, electronicsignals, data packets, memory read/writes, and other known computer,processor, and/or process related communication methodologies.

References to “first network,” “first subscription,” “second network”and “second subscription” are arbitrary and are used to refer to two ormore subscriptions/networks generally because at any given time eithersubscription/network may be in an active mode (on an active voice ordata call) or a standby mode. For example, at a first time, a firstsubscription with a first network may be on an active data call (andthus a “first” subscription) while a second subscription with a secondnetwork is in the standby mode (and thus a “second” subscription), andat a second time, the second subscription may enter an active data call(becoming the “first” subscription) and the first subscription may enterthe standby mode (becoming the “second” subscription). Also, referencesto “first” and “second” subscriptions and networks is not intended toimply that the embodiments are limited to two subscriptions sharing oneradio frequency (RF) resource, because three or more subscriptions mayshare one RF resource provided that only one subscription can use the RFresource at a time. Third and fourth subscriptions would behave similarto a second subscription. Therefore, in the interest of brevity,operations of subscriptions in the standby mode that share the RFresource during tune-away periods are described generally with referenceto the “second” subscription.

In multi-subscription multi-standby communication devices, only onesubscription may use each RF resource chain to communicate with itscommunication network at a time. Even when a subscription is in an idlemode or a standby mode, meaning the subscription is not activelycommunicating with the network, the subscription may still need toperiodically receive access to a shared RF resource chain in order toperform various network operations. For example, an idle subscriptionmay need the shared RF resource chain at regular intervals to performidle mode operations, to receive network-paging messages in order toremain connected to the network, etc. on behalf of its subscription.Therefore, it is possible that at a certain times the multiplesubscriptions sharing an RF resource chain may need to use the RFresource chain to communicate with their respective mobile networkssimultaneously.

The multi-subscription multi-standby communication device may force asubscription that is actively using a shared RF resource chain tointerrupt its RF operations so that an idle subscription may use theshared RF resource chain to perform idle-standby mode operations. Thisprocess of switching access of the shared RF resource chain from theactive subscription to the idle subscription is sometimes referred to asa “tune-away” as the RF resource chain must tune away from the frequencybands and/or channels of the active subscription and tune to frequencybands/channels of the idle subscription. After network communicationsvia the idle subscription are complete, the communication device mayswitch RF resource chain access back from the idle subscription to theactive subscription. Examples of idle-standby mode operations mayinclude one or more of page monitoring (e.g., discontinuous reception),system information monitoring (e.g., receiving and decoding a broadcastcontrol channel), cell reselection measurements to determine whether toinitiate reselection operations to a neighboring cell, updating thesecond subscription network with the current location of themulti-standby communication device, receiving Short Message Service(SMS) messages, and receiving mobile-terminated calls (sometimescollectively referred to herein as tune-away operations).

As a result of the tune-away, data received from the active subscriptionmay be lost or corrupted and thus may be difficult or impossible todecode. The tune-away may thus decrease the throughput of communicationsbetween the multi-subscription multi-standby communication device andthe communication network of the active subscription, and may degradethe quality of an active communication session over the communicationnetwork. The problem of data loss during a tune-away may also impact theuser experience when the first subscription is conducting communicationsthat are particularly sensitive to latency or data loss, such asstreaming media, for example, eMBMS (Evolved Multimedia BroadcastMulticast Service). Thus, operations performed by a processor of amulti-subscription multi-standby communication device may includedetermining whether to permit or prevent a scheduled tune-away. Theimpact of tune-aways on data reception using a first subscription mayincrease when, for example, the MSMS communication device includes twoor more additional subscriptions that the MSMS communication device mustmonitor in addition to receiving data using the first subscription.

Various embodiments enable a processor of a multi-subscriptionmulti-standby communication device to permit or to block a scheduledtune-away based on current and estimated data reception and data loss toimprove to data reception of a data stream. Typically, tune-aways areperiodically scheduled according to a timing dictated by a RAT. However,a processor of a multi-subscription multi-standby communication devicemay determine whether to permit or prevent a given tune-away.

Media files may be divided into segments for transport to thecommunication device. Each segment may be sent to the communicationdevice in a number of bursts. Each burst may include a number ofsubframes. Data in a segment (segment data) may include media data(e.g., content data) and error correction data (such as forward errorcorrection (FEC) data) that may enable the receiver device to recover asegment when some media data is lost or corrupted during transmission.Thus, in many cases the multi-subscription multi-standby communicationdevice does not need to receive all of the data of the segment in orderto recover the segment because error correction data in the receivedportions of the segment can be used to recover the segment from lessthan all of the media data. In some embodiments, the multi-subscriptionmulti-standby communication device may calculate or determine apermitted data loss from a segment based on an amount of media data orcontent data and an amount of error correction data in the segment.

In various embodiments, the MSMS communication device may monitor a dataloss from a broadcast data stream during reception of the data stream bythe MSMS communication device. In some embodiments, the MSMScommunication device may monitor the data loss from (e.g., during) asegment of the broadcast data stream (e.g., the MSMS communicationdevice may monitor data loss from the data stream on a per-segmentbasis) The monitored data loss may be caused at least in part byperforming one or more tune aways to one or more of the subscriptions(i.e., to a second subscription, a third subscription, etc.). In someembodiments, the MSMS communication device may determine a portion ofthe overall data loss that is attributable to each of the subscriptionsto which the MSMS communication device tunes away its RF resource chain.In some embodiments, the MSMS communication device may block or preventtune-aways to the third subscription based on an amount of the monitoreddata loss plus an expected amount of data loss from an anticipatedtune-away to the third subscription meets (e.g., exceeds) a data lossthreshold. In some embodiments, the MSMS communication device may blockone or more tune-aways to the third subscription on a segment by segmentbasis (e.g., may block one or more tune-aways during reception of onesegment, but not during reception of another segment).

In some embodiments, the MSMS communication device may use a data lossthreshold for each subscription to determine whether to block tune-awaysto each subscription. For example, the MSMS communication device may seta separate data loss threshold for the second subscription and the thirdsubscription, and may block tune-aways to a subscription when tune-awaysto that subscription cause data loss above that subscription's data lossthreshold. The MSMS communication device may also adjust eachsubscriptions data loss threshold to change the likelihood of blockingtune-aways to each subscription. In various embodiments, the MSMScommunication device may lower the data loss threshold for the thirdsubscription based on data loss caused by tune-aways to the secondsubscription. In some embodiments, the MSMS communication device mayadjust the third subscription data loss threshold based on an amount ofdata loss caused by the tune-aways to the second subscription.

In some embodiments, the second subscription may be assigned a higherpriority than the third subscription, so that the MSMS communicationdevice may block tune-aways to the third subscription, rather than tothe second subscription. For example, a network operator may prioritizeone subscription over another to bias the MSMS communication device tousing a first subscription network more frequently than a secondsubscription network. As another example, a user of the MSMScommunication device may similarly prefer to use a first subscription(e.g., a work-related subscription) over a second subscription (e.g., apersonal subscription).

As another example, the MSMS communication device may determine that thesecond subscription includes a less frequent tune-away cycle (e.g., apaging cycle) than the third subscription. Because blocking tune-awaysto the third subscription may block fewer opportunities to receive dataon the third subscription than opportunities to receive data on thesecond subscription, the MSMS communication device may prioritize thesecond subscription over the third subscription. For example,Single-Carrier Radio Transmission Technology (1×RTT) has a substantiallylonger paging cycle than Global System for Mobility (GSM)—that is, thereare longer intervals between tune-aways to 1×RTT). Blocking tune-awaysto GSM may result in fewer missed paging messages than blockingtune-aways to 1×RTT.

As another example, the MSMS communication device may determine arelative priority of subscriptions based on a number of collisionsbetween data stream/segment reception and tune-aways to eachsubscription. For example, the MSMS communication device may determinethat the second subscription is experiencing fewer collisions betweenits tune-aways and data stream reception than the third subscription,and the MSMS communication device may block tune-aways to the thirdsubscription to increase overall data stream reception.

In some embodiments, the MSMS communication device may stop blockingtune-aways to the third description in response to detecting a tune-awayto the second subscription that overlaps/collides with data streamreception. Additionally or alternatively, in some embodiments, the MSMScommunication device may stop blocking tune-aways to the thirddescription for a particular segment of the data stream in response todetermining that no further tune-aways to the second subscription arescheduled during the remainder of the segment.

In some embodiments, the MSMS communication device may probabilisticallyapply tune-away blocking in order to only block tune-aways to the thirdsubscription during some segments and not during others. For example,the MSMS communication device may determine whether to block or not toblock a tune-away to the third subscription in a random manner.

Various embodiments may be implemented in multi-subscriptionmulti-standby communication devices that may operate within a variety ofcommunication systems particularly systems that include two or morecommunication networks. FIG. 1 illustrates a communication system 100suitable for use with various embodiments. A multi-subscriptionmulti-standby communication device 110 may communicate with the firstcommunication network 102 through a communication link 132 to the firstbase station 130. In some embodiments, the multi-subscriptionmulti-standby communication device 110 may include a multi-subscriptionmulti-standby (MSMS) communication device. The multi-subscriptionmulti-standby communication device 110 may also communicate with thesecond mobile network 104 through a communication link 142 to the secondbase station 140. The first base station 130 may communicate with thefirst communication network 102 over a wired or wireless communicationlink 134, and the second base station 140 may communicate with thesecond communication network 104 over a wired or wireless communicationlink 144. The communication links 134 and 144 may include fiber opticbackhaul links, microwave backhaul links, and other similarcommunication links.

Each of the communication networks 102 and 104 may supportcommunications using one or more RATs, and each of the wirelesscommunication links 132 and 142 may include cellular connections thatmay be made through two-way wireless communication links using one ormore RATs. Examples of RATs may include 3GPP Long Term Evolution (LTE),GSM, Worldwide Interoperability for Microwave Access (WiMAX), CodeDivision Multiple Access (CDMA), WCDMA, Time Division Multiple Access(TDMA), 1×RTT, Evolution-Data Optimized (EV-DO), and other RATs. Whilethe communication links 132 and 142 are illustrated as single links,each of the communication links may include a plurality of frequenciesor frequency bands, each of which may include a plurality of logicalchannels. Additionally, each of the communication links 132 and 142 mayutilize more than one RAT.

FIG. 2 is a component block diagram of a multi-subscriptionmulti-standby communication device 200 suitable for implementing variousembodiments. With reference to FIGS. 1 and 2, in various embodiments,the multi-subscription multi-standby communication device 200 may besimilar to the multi-subscription multi-standby communication device110. The multi-subscription multi-standby communication device 200 mayinclude a first SIM interface 202 a, which may receive a first identitymodule SIM-1 204 a that may be associated with a first subscription. Themulti-subscription multi-standby communication device 200 may optionallyalso include a second SIM interface 202 b, which may receive a secondidentity module SIM-2 204 b that may be associated with a secondsubscription. The multi-subscription multi-standby communication device200 may optionally include additional SIM interfaces (not illustrated)which may receive an additional identity module.

A SIM in various embodiments may be a Universal Integrated Circuit Card(UICC) that is configured with SIM and/or USIM (Universal SubscriberIdentity Module) applications, enabling access to, for example, GSMand/or Universal Mobile Telecommunications System (UMTS) networks. TheUICC may also provide storage for a phone book and other applications.Alternatively, in a CDMA network, a SIM may be a UICC removable useridentity module (R-UIM) or a CDMA subscriber identity module (CSIM) on acard. Each SIM card may have a CPU, ROM, RAM, EEPROM and I/O circuits. ASIM used in various embodiments may contain user account information, aninternational mobile subscriber identity (IMSI), a set of SIMapplication toolkit (SAT) commands and storage space for phone bookcontacts. A SIM card may further store a Home-Public-Land-Mobile-Network(HPLMN) code to indicate the SIM card network operator provider. AnIntegrated Circuit Card Identity (ICCID) SIM serial number may beprinted on the SIM card for identification.

The multi-subscription multi-standby communication device 200 mayinclude at least one controller, such as a general-purpose processor206, which may be coupled to a coder/decoder (CODEC) 208. The CODEC 208may in turn be coupled to a speaker 210 and a microphone 212. Thegeneral-purpose processor 206 may also be coupled to at least one memory214. The memory 214 may be a non-transitory computer-readable storagemedium that stores processor-executable instructions. The memory 214 maystore an operating system (OS), as well as user application software andexecutable instructions. The memory 214 may also store application data,such as an array data structure.

The general-purpose processor 206 may be coupled to a modem 230. Themodem 230 may include at least one baseband modem processor 216, whichmay be coupled to a memory 222 and a modulator/demodulator 228. Thebaseband modem processor 216 may include physically or logicallyseparate baseband modem processors (e.g., BB1, BB2). Themodulator/demodulator 228 may receive data from the baseband modemprocessor 216 and may modulate a carrier signal with encoded data andprovide the modulated signal to the RF resource 218 for transmission.The modulator/demodulator 228 may also extract an information-bearingsignal from a modulated carrier wave received from the RF resource 218,and may provide the demodulated signal to the baseband modem processor216. The modulator/demodulator 228 may be or include a digital signalprocessor (DSP).

In some optional embodiments, the multi-subscription multi-standbycommunication device 200 may include an optional RF resource 219configured similarly to the RF resource 218 and coupled to an optionalwireless antenna 221. In such embodiments, the multi-subscriptionmulti-standby communication device 200 may leverage the multiple RFresources 218, 219 and antennae 220, 221 to perform diversity receiverreception during a tune-away.

The baseband modem processor 216 may read and write information to andfrom the memory 222. The memory 222 may also store instructionsassociated with a protocol stack, such as protocol stack S1 222 a andprotocol stack S2 222 b. The protocol stacks S1 222 a, S2 222 bgenerally include computer executable instructions to enablecommunication using a radio access protocol or communication protocol.Each protocol stack S1 222 a, S2 222 b typically includes networkprotocol layers structured hierarchically to provide networkingcapabilities. The modem 230 may include one or more of the protocolstacks S1 222 a, S2 222 b to enable communication using one or moreRATs. The protocol stacks S1 222 a, S2 222 b may be associated with aSIM card (e.g., SIM-1 204 a, SIM-2 204 b) configured with asubscription. For example, the protocol stack S1 222 a and the protocolstack S2 222 b may be associated with the SIM-1 204 a. The illustrationof only two protocol stacks S1 222 a, S2 222 b is not intended as alimitation, and the memory 222 may store more than two protocol stacks(not illustrated).

Each SIM and/or RAT in the multi-subscription multi-standbycommunication device 200 (e.g., SIM-1 204 a, SIM-2 204 b) may be coupledto the modem 230 and may be associated with or permitted to use an RFresource. The term “RF resource chain” may be used to refer to all ofthe circuitry used to send and/or receive RF signals, which may includethe baseband modem processor 216 that performs baseband/modem functionsfor communicating with/controlling a RAT, one or more radio unitsincluding transmitter and receiver components that are shown as RFresource 218, and optional RF resource 219, one or more of the wirelessantenna 220 and the optional wireless antenna 221, and additionalcircuitry that may include one or more amplifiers and radios. In someembodiments, an RF resource may share a common baseband modem processor216 (i.e., a single device that performs baseband/modem functions forall RATs on the multi-subscription multi-standby communication device).In some embodiments, each RF resource may include the physically orlogically separate baseband processors (e.g., BB1, BB2).

The RF resources 218, 219 may include transceivers associated with oneor more RATs and may perform transmit/receive functions for themulti-subscription multi-standby communication device 200 on behalf oftheir respective RATs. The RF resources 218, 219 may include separatetransmit and receive circuitry. In some embodiments, the RF resources218, 219 may include only receive circuitry. The RF resources 218, 219may each be coupled to a wireless antenna (e.g., the first wirelessantenna 220 and the second wireless antenna 221). The RF resources 218,219 may also be coupled to the modem 230 (e.g., via themodulator/demodulator 228, the baseband modem processor 216, or anothercomponent).

In some embodiments, the general-purpose processor 206, memory 214,baseband processor(s) 216, and the RF resources 218, 219 may be includedin the multi-subscription multi-standby communication device 200 as asystem-on-chip. In some embodiments, the first and second SIMs 204 a,204 b and their corresponding interfaces 202 a, 202 b may be external tothe system-on-chip. Further, various input and output devices may becoupled to components on the system-on-chip, such as interfaces orcontrollers. Example user input components suitable for use in themulti-subscription multi-standby communication device 200 may include,but are not limited to, a keypad 224 and a touchscreen display 226.

In some embodiments, the keypad 224, the touchscreen display 226, themicrophone 212, or a combination thereof may perform the function ofreceiving the request to initiate an outgoing call. For example, thetouchscreen display 226 may receive a selection of a contact from acontact list or receive a telephone number. In another example, eitheror both of the touchscreen display 226 and microphone 212 may performthe function of receiving a request to initiate an outgoing call. Forexample, the touchscreen display 226 may receive selection of a contactfrom a contact list or receive a telephone number. As another example,the request to initiate the outgoing call may be in the form of a voicecommand received via the microphone 212. Interfaces may be providedbetween the various software modules and functions in themulti-subscription multi-standby communication device 200 to enablecommunication between them.

Functioning together, the two SIMs 204 a, 204 b, the basebandprocessor(s) 216, RF resources 218, 219, and the antennas 220, 221 mayenable communications on two or more RATs. For example, one SIM,baseband processor, and RF resource may be configured to support twodifferent RATs. In some embodiments, more RATs may be supported on themulti-subscription multi-standby communication device 200 by adding moreSIM cards, SIM interfaces, RF resources, and antennas for connecting toadditional mobile networks.

The multi-subscription multi-standby communication device 200 mayoptionally include a tune-away management unit 232 configured to managethe respective access of subscriptions associated with the first andsecond SIMs 204 a, 204 b to the RF resource 218 (and optionally the RFresource 219) in anticipation of or during a tune-away. In someembodiments, the tune-away management unit 232 may determine whether toinitiate a tune-away from a first subscription to a second subscriptionor to a third subscription or whether to prevent or block a tune-away inorder to improve data reception on the first subscription during theduration of the tune-away. In some embodiments, the tune-away managementunit 232 may be implemented within the general-purpose processor 206. Inother embodiments, the tune-away management unit 232 may be implementedas a separate hardware component (i.e., separate from thegeneral-purpose processor 206). In some embodiments, the tune-awaymanagement unit 232 may be implemented as a software application storedwithin the memory 214 and executed by the general-purpose processor 206.

FIG. 3 illustrates a timeline 300 of a reception of segments of a datastream by an RF resource of a multi-subscription multi-standbycommunication device (e.g., the multi-subscription multi-standbycommunication device of FIGS. 1 and 2) according to some embodiments.With reference to FIGS. 1-3, a media file may be divided into portionsfor transport to the multi-subscription multi-standby communicationdevice. For example, in the Dynamic Adaptive Streaming over HTTP (DASH)protocol, the media file may be divided into segments 302 a, 302 b, and302 c. Each segment may be sent to the communication device in one ormore bursts 304 (e.g., 304 a-304 e), which may be interspersed with oneor more idle periods 310. Data in a segment (segment data) may includemedia data (e.g., content data) and error correction data (such asforward error correction (FEC) data) that may enable the receiver deviceto recover a segment when some media data is lost or corrupted duringtransmission.

The multi-subscription multi-standby communication device (e.g., themulti-subscription multi-standby communication devices 110 and 200) mayreceive the data stream using the first subscription. A processor (e.g.,the general-purpose processor 206 and/or the baseband modem processor216) of the multi-subscription multi-standby communication device (i.e.,a device processor) may also cause the device to perform one or moretune-aways from the first subscription to a second subscription and/orto a third subscription. Typically, tune-aways are periodicallyscheduled according to a timing dictated by a RAT. During the tune-away,an amount of data transmitted on the first subscription may be lost orcorrupted and thus may be difficult or impossible to decode. Forexample, a tune-away 306 a to the second subscription may collide (e.g.,overlap in time with) the reception of a burst 304 b on the firstsubscription during a segment 302 a. As another example, a tune-away 308a to the third subscription may collide with the reception of a burst304 a on the first subscription. A tune-away that collides with thereception of segment data may thus decrease the throughput ofcommunications between the multi-subscription multi-standbycommunication device and the communication network of the firstsubscription, and may degrade the quality of the communication sessionover the first communication network. The problem of data loss during atune-away may also impact the user experience when the firstsubscription is conducting communications that are particularlysensitive to latency or data loss, such as streaming media. Thus, invarious embodiments, the device processor may determine whether topermit or prevent a given tune-away.

A radio access technology may provide a periodic tune away cycle ortiming, which may vary from RAT to RAT. For example, the secondsubscription may have a less frequent tune-away cycle than the thirdsubscription. In such case, while the third subscription (with morefrequently-scheduled tune-aways) may have more collisions with datareception on the first subscription than the second subscription,blocking tune aways to the third subscription may block feweropportunities to receive data on the third subscription thanopportunities to receive data on the second subscription. For example,during the reception of segments 302 a, 302 b, and 302 c, tune-aways 306a and 306 c to the second subscription may collide with bursts 304 b and304 e on the first subscription, respectively. During the same timeperiod, tune-aways 308 a, 308 c, and 308 d to the third subscription maycollide with bursts 304 a, 304 c, and 304 d on the first subscription,respectively. Some tune-aways (e.g., tune-away 306 b to the secondsubscription, and tune-away 308 b to the third subscription) and somedata bursts on the first subscription (e.g., burst 304 f) may notexperience a collision.

Because the third subscription has a shorter tune-away cycle (i.e.,schedules tune-away more frequently) when the second subscription,blocking tune-aways to the third subscription may result in fewer missedopportunities to receive data over the third subscription than blockingtune-aways to the second subscription. Thus, in some embodiments, theMSMS communication device may prioritize the second subscription overthe third subscription.

Additionally or alternatively, the MSMS communication device maydetermine that there are fewer collisions between tune-aways to thesecond subscription and first subscription data reception thancollisions between tune-aways to the third subscription and firstsubscription data reception. Thus, in some embodiments, the MSMScommunication device may prioritize the second subscription over thethird subscription based on a number of collisions between datastream/segment reception and tune-aways to each subscription.

FIG. 4 illustrates a method 400 for managing a tune-away by an RFresource of a multi-subscription multi-standby (MSMS) communicationdevice according to some embodiments. With reference to FIGS. 1-4, themethod 400 may be implemented by a multi-subscription multi-standbycommunication device (e.g., the multi-subscription multi-standbycommunication device 102, 200), such as under the control of a processor(e.g., the general-purpose processor 206, the baseband processor 216, aseparate controller, and/or the like) of the multi-subscriptionmulti-standby communication device (i.e., a device processor).

In block 402, the device processor may receive segment data of a datastream using a first subscription (e.g., “SUB1”). In block 404, thedevice processor may monitor a data loss during a segment of the datastream. For example, a running data loss during the segment may bedetermined as a total amount of data loss at the end of each burst ofthe currently-received segment of the data stream (e.g., “L”). Thedevice processor may update and monitor the running data loss during thereceipt of each segment of the data stream. In some embodiments, theMSMS communication device may determine the amount of data loss based onan amount of segment data expected to be received and an amount of thesegment data actually received by the MSMS communication device. Thedevice processor may determine the amount of expected segment data basedon information received by the MSMS communication device in the datastream (for example, multicast traffic channel (MCH) schedulinginformation (MSI)).

In block 406, the device processor may determine an amount of expectedor anticipated data loss that will be caused by (e.g., attributable to)future tune-aways to all subscriptions (e.g., “LTA”) during the segment.The device processor may determine the expected amount of data lossbefore the future tune away(s) occurs. In some embodiments, the deviceprocessor may determine an amount of expected data loss that will becaused by upcoming tune-aways to the second subscription and to thethird subscription during the currently-received segment of the datastream. In some embodiments, the device processor may determine theportions of data loss attributable to each subscription has a measuredamount of data lost (e.g., a number of bytes or kilobytes) duringcollisions between expected data reception and future tune away(s).

In various embodiments, the device processor may determine the amount ofexpected data loss from anticipated tune-aways at one or more timesduring the currently-received segment. In some embodiments, the deviceprocessor may determine the amount of expected data loss before, after,and/or during each burst of the segment. In some embodiments, the deviceprocessor may determine the amount of expected data loss before, after,and/or during each idle period during the segment. In some embodiments,the device processor may determine the amount of expected data loss withgreater or lesser granularity (i.e., more frequently, or lessfrequently).

In block 408, the device processor may determine whether the monitoreddata loss (e.g., L) plus the amount of expected data loss caused byanticipated tune-aways (e.g., LTA) meets (e.g., is greater than) a firstdata loss threshold (e.g., “TH1”). In response to determining that themonitored data loss plus the expected data loss meets the firstthreshold (i.e., determination block 408=“Yes”), the device processormay prevent tune-aways to the second subscription and to the thirdsubscription in block 410. In some embodiments, the device processor mayprevent tune-aways to the second subscription and the third subscriptionfor the remainder of the segment of the data stream. The deviceprocessor may continue to receive segment data of the data stream usingthe first subscription in block 402.

In response to determining that the monitored data loss plus theexpected data loss does not meet the first threshold (i.e.,determination block 408=“No”), the device processor may determinewhether the next tune-away is a tune-away from the first subscription tothe third subscription (e.g., “SUB3”) in determination block 412.

In response to determining that the next tune-away is not to the thirdsubscription (i.e., determination block 412=“No”), the device processormay permit tune-aways to the second subscription (e.g., “SUB2”) in block420. The device processor may continue to receive segment data of thedata stream using the first subscription in block 402.

In response to determining that the next tune-away is to the thirdsubscription (i.e., determination block 412=“Yes”), the device processormay determine whether the monitored data loss (e.g., L) plus an amountof data loss anticipated during the upcoming tune-away to the thirdsubscription (e.g., “LTA3”) meets (e.g., is greater than) a second dataloss threshold (e.g., “TH2”) in determination block 414.

In response to determining that the monitored data loss plus the amountof data loss anticipated during the upcoming tune-away to the thirdsubscription meets the second data loss threshold (i.e., determinationblock 414=“Yes”), the device processor may prevent (i.e., block) theupcoming tune-away to the third subscription in block 416.

In response to determining that the monitored data loss plus the amountof data anticipated during the upcoming tune-away to the thirdsubscription does not meet the second data loss threshold (i.e.,determination block 414=“No”), the device processor may permit theupcoming tune-away to the third subscription in block 418.

In block 420, the device processor may permit one or more upcomingtune-aways to the second subscription. The device processor may continueto receive segment data of the data stream using the first subscriptionin block 402.

FIG. 5 illustrates a method 500 for managing a tune-away by an RFresource of an MSMS communication device according to some embodiments.With reference to FIGS. 1-5, the method 500 may be implemented by amulti-subscription multi-standby communication device (e.g., themulti-subscription multi-standby communication device 102, 200), such asunder the control of a processor (e.g., the general-purpose processor206, the baseband processor 216, a separate controller, and/or the like)of the multi-subscription multi-standby communication device (i.e., adevice processor). In blocks 402-420, the device processor may performoperations of like-numbered blocks of the method 400 as described.

In response to determining that the next tune-away is to the thirdsubscription (i.e., determination block 412=“Yes”), the device processormay determine an amount of the monitored data loss (e.g., L) that isattributable to (e.g., caused by) past tune-aways (e.g., previoustune-aways during the present segment) to the second subscription inblock 501.

In block 502, the device processor may determine an amount of reductionof the second data loss threshold (e.g., TH2) based on the amount of themonitored data loss that is attributable to past tune-aways to thesecond subscription. In some embodiments, the amount of reduction of thesecond data loss threshold may directly reflect the determined portionof data loss that is attributable to the second subscription. Forexample, if tune-aways to the second subscription are responsible for adata loss of 20 kB, the device processor may determine the amount ofreduction of the second data loss threshold to be 20 kB. In someembodiments, the amount of reduction of the second data loss thresholdmay be proportional to the determined portion of data loss that isattributable to the second subscription. In some embodiments, the deviceprocessor may use the portion of data loss that is attributable to thesecond subscription as a factor in determining the amount of reductionof the second data loss threshold.

In block 504, the device processor may reduce the second data lossthreshold by the determined amount of reduction. In determination block506, the device processor may determine whether the monitored data lossplus the amount of data loss anticipated during the upcoming tune-awayto the third subscription meets (e.g., is greater than) the reducedsecond data loss threshold. In response to determining that themonitored data loss plus the amount of data loss anticipated during theupcoming tune-away to the third subscription meets the reduced seconddata loss threshold (i.e., determination block 506=“Yes”), the deviceprocessor may prevent (i.e., block) the upcoming tune-away to the thirdsubscription in block 416.

In response to determining that the monitored data loss plus the amountof data loss anticipated during the upcoming tune-away to the thirdsubscription does not meet the reduced second data loss threshold (i.e.,determination block 506=“No”), the device processor may permit theupcoming tune-away to the third subscription in block 418.

FIG. 6 illustrates a method 600 for managing a tune-away by an RFresource of an MSMS communication device according to some embodiments.With reference to FIGS. 1-6, the method 600 may be implemented by amulti-subscription multi-standby communication device (e.g., themulti-subscription multi-standby communication device 102, 200), such asunder the control of a processor (e.g., the general-purpose processor206, the baseband processor 216, a separate controller, and/or the like)of the multi-subscription multi-standby communication device (i.e., adevice processor). In blocks 402-420 and blocks 502-506, the deviceprocessor may perform operations of like-numbered blocks of the methods400 and 500 as described.

In block 602, the device processor may determine whether a collision isdetected between segment data reception using the first subscription anda tune-away to the second subscription. In response to determining thatno collision is detected between segment data reception using the firstsubscription and the tune-away to the second subscription (i.e.,determination block 602=“No”), the device processor may continue toreceive segment data of the data stream using the first subscription inblock 402.

In response to determining that a collision is detected between segmentdata reception using the first subscription and the tune-away to thesecond subscription (i.e., determination block 602=“Yes”), the deviceprocessor may increase the second data loss threshold. For instance, thedevice processor may increase the second data loss threshold by thedetermined amount of reduction (e.g., the device processor may restorethe second data loss threshold to its pre-reduction value) in block 604.Thus, in some embodiments, the device processor may stop preferentiallyblocking/preventing tune-aways to the third subscription in response todetermining that the tune-away to the second subscription collides withreception of the data stream (e.g., reception of the present segment ofthe data stream) on the first subscription.

FIG. 7 illustrates a method 700 for managing a tune-away by an RFresource of an MSMS communication device according to some embodiments.With reference to FIGS. 1-7, the method 700 may be implemented by amulti-subscription multi-standby communication device (e.g., themulti-subscription multi-standby communication device 102, 200), such asunder the control of a processor (e.g., the general-purpose processor206, the baseband processor 216, a separate controller, and/or the like)of the multi-subscription multi-standby communication device (i.e., adevice processor). In blocks 402-420 and blocks 502-506, the deviceprocessor may perform operations of like-numbered blocks of the methods400 and 500 as described.

In some embodiments, the device processor may stop preferentiallyblocking tune-aways to the third subscription if doing so may notimprove overall reception of the data stream using the firstsubscription. For example, in determination block 702, the deviceprocessor may determine whether another collision will occur between thefirst subscription (e.g., reception of the data stream using the firstsubscription) and a tune-away to the second subscription during thereception of the present segment of the data stream. In response todetermining that there will be another collision between the firstsubscription and the second subscription (i.e., determination block702=“Yes”), the device processor may continue to receive segment data ofthe data stream using the first subscription in block 402. The deviceprocessor may also continue to use the reduced second data lossthreshold to determine whether the portion of data loss attributable totune-aways to third subscription satisfies the reduced second data lossthreshold.

In response to determining that there will not be another collisionbetween the first subscription and the second subscription (i.e.,determination block 702=“No”), then the device processor may increasethe second data loss threshold by the determined amount of reduction(e.g., the device processor may restore the second data loss thresholdto its pre-reduction value) in block 704.

FIG. 8 illustrates a method 800 for managing a tune-away by an RFresource of an MSMS communication device according to some embodiments.With reference to FIGS. 1-8, the method 800 may be implemented by amulti-subscription multi-standby communication device (e.g., themulti-subscription multi-standby communication device 102, 200), such asunder the control of a processor (e.g., the general-purpose processor206, the baseband processor 216, a separate controller, and/or the like)of the multi-subscription multi-standby communication device (i.e., adevice processor). In blocks 402-420 the device processor may performoperations of like-numbered blocks of the method 400 as described.

In some embodiments, the MSMS communication device may probabilisticallyapply tune-away blocking in order to only block tune-aways to the thirdsubscription during some segments and not during others. For example, inblock 802, the device processor may determine a biased block probabilitythreshold. In some embodiments, the biased block probability thresholdmay be represented by R, and the device processor may determine a valuefor R such that 0≦R≦1. In block 804, the device processor may determinea random (or pseudorandom) number for the present segment (e.g., thesegment of the data stream that the MSMS communication device iscurrently receiving).

In determination block 806, the device processor may determine whetherthe determined random number meets (e.g., is greater than) the biasedblock probability threshold. In response to determining that thedetermined random number meets (e.g., is greater than) the biased blockprobability threshold (i.e., determination block 806=“Yes”), the deviceprocessor may permit tune-aways to the third subscription in block 418.The device processor may then permit tune-aways to the secondsubscription in block 420.

In response to determining that the determined random number does notmeet (e.g., is not greater than) the biased block probability threshold(i.e., determination block 806=“No”), the device processor may determinewhether the next tune-away is a tune-away from the first subscription tothe third subscription (e.g., “SUB3”) in determination block 412.

Various embodiments illustrated and described are provided merely asexamples to illustrate various features of the claims. However, featuresshown and described with respect to any given embodiment are notnecessarily limited to the associated embodiment and may be used orcombined with other embodiments that are shown and described. Further,the claims are not intended to be limited by any one example embodiment.For example, one or more of the operations of the methods 400, 500, 600,700, and 800 may be substituted for or combined with one or moreoperations of the methods 400, 500, 600, 700, and 800.

Various embodiments (including, but not limited to, embodimentsdescribed with reference to FIGS. 1-8) may be implemented in any of avariety of multi-subscription multi-standby communication devices, anexample of which (e.g., multi-subscription multi-standby communicationdevice 900) is illustrated in FIG. 9. With reference to FIGS. 1-9, invarious embodiments, the multi-subscription multi-standby communicationdevice 900 (which may correspond, for example, to the multi-subscriptionmulti-standby communication devices 102 and 200) may include a processor902 coupled to a touchscreen controller 904 and an internal memory 906.The processor 902 may be one or more multi-core integrated circuitsdesignated for general or specific processing tasks. The internal memory906 may be volatile or non-volatile memory, and may also be secureand/or encrypted memory, or unsecure and/or unencrypted memory, or anycombination thereof. The touchscreen controller 904 and the processor902 may also be coupled to a touchscreen panel 912, such as aresistive-sensing touchscreen, capacitive-sensing touchscreen, infraredsensing touchscreen, etc. Additionally, the display of themulti-subscription multi-standby communication device 900 need not havetouch screen capability.

The multi-subscription multi-standby communication device 900 may havetwo or more radio signal transceivers 908 (e.g., Peanut, Bluetooth,ZigBee, Wi-Fi, RF radio) and antennae 910, for sending and receivingcommunications, coupled to each other and/or to the processor 902. Thetransceivers 908 and antennae 910 may be used with the above-mentionedcircuitry to implement the various wireless transmission protocol stacksand interfaces. The multi-subscription multi-standby communicationdevice 900 may include one or more cellular network wireless modemchip(s) 916 coupled to the processor and antennae 910 that enablescommunication via two or more cellular networks via two or more radioaccess technologies.

The multi-subscription multi-standby communication device 900 mayinclude a peripheral device connection interface 918 coupled to theprocessor 902. The peripheral device connection interface 918 may besingularly configured to accept one type of connection, or may beconfigured to accept various types of physical and communicationconnections, common or proprietary, such as USB, FireWire, Thunderbolt,or PCIe. The peripheral device connection interface 918 may also becoupled to a similarly configured peripheral device connection port (notshown).

The multi-subscription multi-standby communication device 900 may alsoinclude speakers 914 for providing audio outputs. The multi-subscriptionmulti-standby communication device 900 may also include a housing 920,constructed of a plastic, metal, or a combination of materials, forcontaining all or some of the components discussed herein. Themulti-subscription multi-standby communication device 900 may include apower source 922 coupled to the processor 902, such as a disposable orrechargeable battery. The rechargeable battery may also be coupled tothe peripheral device connection port to receive a charging current froma source external to the multi-subscription multi-standby communicationdevice 900. The multi-subscription multi-standby communication device900 may also include a physical button 924 for receiving user inputs.The multi-subscription multi-standby communication device 900 may alsoinclude a power button 926 for turning the multi-subscriptionmulti-standby communication device 900 on and off.

The processor 902 may be any programmable microprocessor, microcomputeror multiple processor chip or chips that can be configured by softwareinstructions (applications) to perform a variety of functions, includingthe functions of various embodiments described below. In somemulti-subscription multi-standby communication devices, multipleprocessors 902 may be provided, such as one processor dedicated towireless communication functions and one processor dedicated to runningother applications. Typically, software applications may be stored inthe internal memory 906 before they are accessed and loaded into theprocessor 902. The processor 902 may include internal memory sufficientto store the application software instructions.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the blocks of various embodiments must be performed in theorder presented. As will be appreciated by one of skill in the art theorder of blocks in the foregoing embodiments may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the blocks; these words are simply used to guidethe reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm blocks described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and blocks have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of variousembodiments.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with theembodiments disclosed herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but, in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of communication devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Alternatively, some blocks ormethods may be performed by circuitry that is specific to a givenfunction.

In various embodiments, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored as one or more instructions orcode on a non-transitory computer-readable medium or non-transitoryprocessor-readable medium. The operations of a method or algorithmdisclosed herein may be embodied in a processor-executable softwaremodule, which may reside on a non-transitory computer-readable orprocessor-readable storage medium. Non-transitory computer-readable orprocessor-readable storage media may be any storage media that may beaccessed by a computer or a processor. By way of example but notlimitation, such non-transitory computer-readable or processor-readablemedia may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to store desired programcode in the form of instructions or data structures and that may beaccessed by a computer. Disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk, and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofnon-transitory computer-readable and processor-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentembodiments. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thescope of the embodiments. Thus, various embodiments are not intended tobe limited to the embodiments shown herein but are to be accorded thewidest scope consistent with the following claims and the principles andnovel features disclosed herein.

What is claimed is:
 1. A method implemented on a multi-subscription multi-standby (MSMS) communication device for managing a tune-away by a radio frequency (RF) resource, comprising: monitoring an amount of data loss from a broadcast data stream received by the MSMS communication device using a first subscription; determining an amount of expected data loss from anticipated tune-aways from the first subscription to a second subscription; determining an amount of expected data loss from anticipated tune-aways from the first subscription to a third subscription; determining whether the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets a first data loss threshold; determining whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets a second data loss threshold, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription does not meet the first data loss threshold; and preventing a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold.
 2. The method of claim 1, further comprising: permitting the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription does not meet the second data loss threshold.
 3. The method of claim 1, further comprising: permitting a tune-away of the RF resource from the first subscription to the second subscription after determining whether the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold.
 4. The method of claim 1, further comprising: preventing tune-aways from the first subscription to the second subscription and to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets the first data loss threshold.
 5. The method of claim 1, wherein preventing a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold comprises: determining an amount of reduction for the second data loss threshold based on an amount of data loss that is attributable to past tune-aways from the first subscription to the second subscription; reducing the second data loss threshold by the determined amount of reduction; determining whether the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the reduced second data loss threshold; and preventing the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the reduced second data loss threshold.
 6. The method of claim 5, further comprising: permitting the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription does not meet the reduced second data loss threshold.
 7. The method of claim 5, further comprising: determining whether a collision between reception of the broadcast data stream and a tune-away from the first subscription to the second subscription is detected; and increasing the second data loss threshold, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is detected.
 8. The method of claim 7, wherein increasing the second data loss threshold comprises increasing the second data loss threshold by the determined amount of reduction, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is detected.
 9. The method of claim 7, further comprising: continuing to receive segment data of the broadcast data stream using the first subscription, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not detected.
 10. The method of claim 7, further comprising: determining whether another collision between reception of the broadcast data stream and a tune-away from the first subscription to the second subscription is expected; and increasing the second data loss threshold, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not expected.
 11. The method of claim 10, wherein increasing the second data loss threshold comprises increasing the second data loss threshold by the determined amount of reduction, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not expected.
 12. The method of claim 10, further comprising: continuing to receive segment data of the broadcast data stream using the first subscription, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is expected.
 13. The method of claim 1, further comprising: determining a biased block probability threshold; determining a random number for a present segment of the broadcast data stream; determining whether the determined random number meets the biased block probability threshold; and permitting tune-aways of the RF resource from the first subscription to the third subscription, in response to determining that the determined random number meets the biased block probability threshold.
 14. The method of claim 13, further comprising: determining whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold, in response to determining that the determined random number does not meet the biased block probability threshold.
 15. A multi-subscription multi-standby (MSMS) communication device, comprising: a memory; a radio frequency (RF) resource; and a processor coupled to the memory and the radio frequency resource and configured with processor-executable instructions to: monitor an amount of data loss from a broadcast data stream received by the MSMS communication device using a first subscription; determine an amount of expected data loss from anticipated tune-aways from the first subscription to a second subscription; determine an amount of expected data loss from anticipated tune-aways from the first subscription to a third subscription; determine whether the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets a first data loss threshold; determine whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets a second data loss threshold, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription does not meet the first data loss threshold; and prevent a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold.
 16. The multi-subscription multi-standby communication device of claim 15, wherein the processor is further configured with processor-executable instructions to permit the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription does not meet the second data loss threshold.
 17. The multi-subscription multi-standby communication device of claim 15, wherein the processor is further configured with processor-executable instructions to permit a tune-away of the RF resource from the first subscription to the second subscription after determining whether the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold.
 18. The multi-subscription multi-standby communication device of claim 15, wherein the processor is further configured with processor-executable instructions to prevent tune-aways from the first subscription to the second subscription and to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets the first data loss threshold.
 19. The multi-subscription multi-standby communication device of claim 15, wherein the processor is further configured with processor-executable instructions to prevent a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold by: determining an amount of reduction for the second data loss threshold based on an amount of data loss that is attributable to past tune-aways from the first subscription to the second subscription; reducing the second data loss threshold by the determined amount of reduction; determining whether the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the reduced second data loss threshold; and preventing the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the reduced second data loss threshold.
 20. The multi-subscription multi-standby communication device of claim 19, wherein the processor is further configured with processor-executable instructions to: permit the tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription does not meet the reduced second data loss threshold.
 21. The multi-subscription multi-standby communication device of claim 19, wherein the processor is further configured with processor-executable instructions to: determine whether a collision between reception of the broadcast data stream and a tune-away from the first subscription to the second subscription is detected; and increase the second data loss threshold, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is detected.
 22. The multi-subscription multi-standby communication device of claim 21, wherein the processor is further configured with processor-executable instructions to: increase the second data loss threshold by the determined amount of reduction, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is detected.
 23. The multi-subscription multi-standby communication device of claim 21, wherein the processor is further configured with processor-executable instructions to: continue to receive segment data of the broadcast data stream using the first subscription, in response to determining that the collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not detected.
 24. The multi-subscription multi-standby communication device of claim 21, wherein the processor is further configured with processor-executable instructions to: determine whether another collision between reception of the broadcast data stream and a tune-away from the first subscription to the second subscription is expected; and increase the second data loss threshold, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not expected.
 25. The multi-subscription multi-standby communication device of claim 24, wherein the processor is further configured with processor-executable instructions to: increase the second data loss threshold by the determined amount of reduction, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is not expected.
 26. The multi-subscription multi-standby communication device of claim 24, wherein the processor is further configured with processor-executable instructions to: continue to receive segment data of the broadcast data stream using the first subscription, in response to determining that the another collision between reception of the broadcast data stream and the tune-away from the first subscription to the second subscription is expected.
 27. The multi-subscription multi-standby communication device of claim 15, wherein the processor is further configured with processor-executable instructions to: determine a biased block probability threshold; determine a random number for a present segment of the broadcast data stream; determine whether the determined random number meets the biased block probability threshold; and permit the tune-aways of the RF resource from the first subscription to the third subscription, in response to determining that the determined random number meets the biased block probability threshold.
 28. The multi-subscription multi-standby communication device of claim 27, wherein the processor is further configured with processor-executable instructions to: determine whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold, in response to determining that the determined random number does not meet the biased block probability threshold.
 29. A multi-subscription multi-standby (MSMS) communication device, comprising: means for monitoring an amount of data loss from a broadcast data stream received by the MSMS communication device using a first subscription; means for determining an amount of expected data loss from anticipated tune-aways from the first subscription to a second subscription; means for determining an amount of expected data loss from anticipated tune-aways from the first subscription to a third subscription; means for determining whether the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets a first data loss threshold; means for determining whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets a second data loss threshold, in response to determining that the amount of the monitored data loss and plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription does not meet the first data loss threshold; and means for preventing a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold.
 30. A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a multi-subscription multi-standby (MSMS) communication device to perform operations comprising: monitoring an amount of data loss from a broadcast data stream received by the MSMS communication device using a first subscription; determining an amount of expected data loss from anticipated tune-aways from the first subscription to a second subscription; determining an amount of expected data loss from anticipated tune-aways from the first subscription to a third subscription; determining whether the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription meets a first data loss threshold; determining whether an amount of the monitored data loss plus an amount of expected data loss from a next anticipated tune-away from the first subscription to the third subscription meets a second data loss threshold, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from anticipated tune-aways from the first subscription to the second subscription plus the amount of expected data loss from anticipated tune-aways from the first subscription to the third subscription does not meet the first data loss threshold; and preventing a tune-away of the RF resource from the first subscription to the third subscription, in response to determining that the amount of the monitored data loss plus the amount of expected data loss from the next anticipated tune-away from the first subscription to the third subscription meets the second data loss threshold. 